Skip to content

fix(tests): use whitelisted smoke job in quantum integration test#461

Open
cursor[bot] wants to merge 2 commits into
mainfrom
cursor/repository-automation-efc4
Open

fix(tests): use whitelisted smoke job in quantum integration test#461
cursor[bot] wants to merge 2 commits into
mainfrom
cursor/repository-automation-efc4

Conversation

@cursor

@cursor cursor Bot commented Jun 20, 2026

Copy link
Copy Markdown

Summary

Hourly repo health automation failed on pre_commit_check because tests/test_quantum_integration.py used the non-whitelisted job name another. The quantum integration bridge only accepts baseline, benchmark, nightly, and smoke, so the test never reached status lookup logic.

Changes

  • Updated test_run_autorun_job_reads_status_for_list_and_dict_shapes to use the whitelisted smoke job name in fixtures and assertions.

Verification

  • pytest tests/test_quantum_integration.py -v — 2 passed
  • Full health cycle: PYTHON_BIN=.venv/bin/python scripts/repo_health_automation.py --once --repair-status --refresh-stale-status --run-agents --continue-on-fail — all steps passed (2725 unit tests, integration contract gate, repo agents)

Checklist

  • I added or updated tests for new behavior
  • I updated relevant documentation (README, .github/copilot-instructions.md, instruction files)
  • All unit tests pass locally (python scripts/test_runner.py --unit)
  • No hardcoded secrets or API keys introduced
  • PR title clearly describes the change (not a generic codespace/branch name)
Open in Web View Automation 

Summary by Sourcery

Bug Fixes:

  • Update quantum integration autorun status test to use the whitelisted smoke job name instead of a non-allowed job, ensuring the test correctly validates status handling and passes in automated health checks.

Note

Low Risk
Test-only rename plus generated status JSON updates; no production or auth logic changed.

Overview
Fixes failing repo health pre_commit_check by aligning the quantum integration unit test with run_autorun_job’s allowed job names (baseline, benchmark, nightly, smoke).

test_run_autorun_job_reads_status_for_list_and_dict_shapes now uses smoke instead of another in parametrized fixtures, the run_autorun_job call, and assertions so dry-run status lookup is actually exercised.

The diff also refreshes data_out/**/status.json (and related CI/smoke artifacts) from a successful health cycle—timestamps, step durations, and resource snapshots only; no application logic changes there.

Reviewed by Cursor Bugbot for commit 27e8080. Bugbot is set up for automated code reviews on this repo. Configure here.

The run_autorun_job bridge validates job names against baseline,
benchmark, nightly, and smoke. Update list/dict status lookup test to
use smoke instead of another so pre-commit unit tests pass.

Co-authored-by: Bryan
Update tracked data_out status files from successful hourly repo health
automation run (2725 tests passed, integration gate and agents ok).

Co-authored-by: Bryan
@sourcery-ai

sourcery-ai Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the quantum integration autorun job test to use the whitelisted 'smoke' job name so the test exercises the real status lookup path accepted by the bridge.

File-Level Changes

Change Details Files
Align quantum integration autorun job test fixtures and assertions with the whitelisted 'smoke' job name so the test reaches status lookup logic.
  • Change parametrized job payloads to use the 'smoke' job name instead of a non-whitelisted name for both list and dict payload shapes.
  • Update the autorun job invocation to request the 'smoke' job so it passes bridge validation.
  • Adjust assertions to expect 'smoke' for job_name and status.name while keeping preset expectations unchanged.
tests/test_quantum_integration.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions github-actions Bot added the tests label Jun 20, 2026
@github-actions

Copy link
Copy Markdown

🟡 Coverage — 7b3a876

Metric Value
Total coverage 65.2%
→ vs main 0.0%
Minimum threshold 60%

Updated on every push · 2026-06-20

@Bryan-Roe Bryan-Roe marked this pull request as ready for review June 22, 2026 00:39
@Bryan-Roe Bryan-Roe self-requested a review as a code owner June 22, 2026 00:39
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@cursor

cursor Bot commented Jun 22, 2026

Copy link
Copy Markdown
Author

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_82c1ddcc-96b9-4bf9-98cc-a6537d006a68)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant